Music composition aid

ABSTRACT

Disclosed herein are computer-implemented method, computer-readable storage medium, and DAW embodiments for implementing a music composition aid. An embodiment includes retrieving a first constraint value, receiving a selection of a set of musical elements, and accepting a second constraint value corresponding to the set of musical elements. Some embodiments further include invoking an iterator function, using at least the second constraint value as an argument, and generating an output of the iterator function, limiting a size of the output of the iterator function, according to the lesser of the first constraint value or a transform of the second constraint value. Output of the iterator function may include, of the set of musical elements, a subset determined by the second constraint value. The size of the output may be no more than the first constraint value. Further embodiments may render the output of the iterator function visually and/or audibly, for example.

BACKGROUND

Whether doing MIDI composition or traditional music notation, manycomposers may start with a blank page. Some may use a step sequencer andmanually click in rhythm ideas, while others may use stamping tools togenerate a single chord or scale. Some composers may load a VST pluginand use a piano roll to input notes manually, while others may useMIDI-capable instruments to play in their ideas into a MIDI format.

Many modern composers (e.g., for film scores, game soundtracks, etc.)are abandoning traditional music notation in favor of MIDI compositionfor relative speed. But the process outlined above is effectively thesame as traditional notation—sitting idly, tinkering by hand until anidea emerges.

Previous tools attempting to expose users to new musical ideas are stillvery limited in terms of variety and efficiency. Separately, many in themusic industry are working toward music automation, in light ofdeadlines and budgets becoming ever tighter. Music automation (e.g.,using only neural networks, artificial intelligence, machine learning,etc.) has posed other problems, however, in that automated solutions usemusic of the past as the input for their training data. As a result, newgenres and ideas remain hidden, because the automated solutions may belocked into a particular style based on their inputs. Moreover,automated composition is generally less gratifying for composers whorely on automation.

Many composers invest significant amounts of money taking classes insongwriting, composition, and music, only to learn that music theory isjust a language to describe how music of the past works. It takes manyyears of music theory to arrive to certain compositional techniques andconclusions. Music theory may be useful at least in terms ofcommunicating to other composers or musicians, but most composers'choices depend on what sounds good subjectively to their ear, and theymay completely ignore the theory.

Such inefficiencies and limitations described above may be a result ofdeficiencies in existing musical tools, but may also result fromselective attention and/or artificial limitations of music theory. Anyof these factors, among other constraints, may unnecessarily limit theoptions that musicians would typically consider.

BRIEF SUMMARY

Disclosed herein are system, apparatus, device, method and/orcomputer-readable storage-medium embodiments, and/or combinations andsub-combinations thereof, for a music composition aid. In this document,the term “user” may be substituted with the term “composer” within thescope of the disclosure contained herein.

In some embodiments, at least one computer processor may retrieve, via amemory, a first constraint value. The at least one computer processormay further receive, via a first module of a user interface, a selectionof a set of musical elements.

In some embodiments, the at least one computer processor may furtheraccept, via a module of a user interface, a second constraint value,corresponding to the set of musical elements, and store the secondconstraint value in memory. The at least one computer processor mayadditionally invoke an iterator function, using at least the secondconstraint value as an argument.

In some embodiments, the at least one computer processor may generate anoutput of the iterator function, limiting a size of the output of theiterator function according to the lesser of the first constraint valueor a transform of the second constraint value. The output of theiterator function may include at least part of a subset of the set ofmusical elements. The subset may be determined by the second constraintvalue, and the size of the output may be less than or equal to the firstconstraint value.

In some embodiments, the at least one computer processor may invoke theiterator function in response to an input via the user interface, forexample, when the output of the iterator function is not already storedin the memory. Moreover, the iterator function may include a coroutine,a generator, or a combination thereof. Additionally, or alternatively,the transform may include an enumerative combinatorial function, forexample.

In some embodiments, the musical elements comprise a melody sequence, achord, a chord note, a chord sequence, a rhythm sequence, a syllable, ora combination thereof. Additionally, or alternatively, the at least onecomputer processor may be integrated in a digital audio workstation(DAW) apparatus. In some embodiments, the rendering may include emittingaudio output and/or displaying video output based at least in part onthe output of the iterator function, for example.

In some embodiments, the at least one processor may further record, inthe memory, metadata corresponding to at least one element of theoutput. Further, the metadata may include an indication of whether agiven musical element of the output has been rendered, a rating, anelement descriptor, a component descriptor, or a mood descriptor, forexample.

Other embodiments, features, and advantages of the invention will be, orwill become, apparent to one with skill in the art upon examination ofthe following drawings/figures and detailed description. It is intendedthat all such additional embodiments, features, and advantages beincluded within this description, be within the scope of thisdisclosure, and be protected by the claims that follow.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are incorporated herein and form a part of thespecification.

FIG. 1 is a flowchart illustrating a process implementing some of theenhanced techniques described herein, according to some embodiments.

FIG. 2 is a screenshot illustrating an example interaction with somecomponents of a user interface including a rhythm tab, according to someembodiments.

FIG. 3 is another screenshot illustrating an example interaction withsome components of a user interface including a rhythm tab, according tosome embodiments.

FIG. 4 is a screenshot illustrating an example interaction with somecomponents of a user interface including a checkbox visualization ofbeats, according to some embodiments.

FIG. 5 is a screenshot illustrating an example interaction with somecomponents of a user interface including a rhythm-length dropdown menu,according to some embodiments.

FIG. 6 is a screenshot illustrating an example interaction with somecomponents of a user interface including rhythm shift buttons, accordingto some embodiments.

FIG. 7 is a screenshot illustrating an example interaction with somecomponents of a user interface a rhythm permutation listing, accordingto some embodiments.

FIG. 8 is a screenshot illustrating an example interaction with somecomponents of a user interface including dropdown menus for beats andMIDI instruments, according to some embodiments.

FIG. 9 is a screenshot illustrating an example interaction with somecomponents of a user interface including a favorite rhythms listing,according to some embodiments.

FIG. 10 is a screenshot illustrating an example interaction with somecomponents of a user interface including rhythm elements and metadata,according to some embodiments.

FIG. 11 is a screenshot illustrating an example interaction with somecomponents of a user interface including a melody tab, according to someembodiments.

FIG. 12 is a screenshot illustrating an example interaction with somecomponents of a user interface including an integer-annotated keyboard,according to some embodiments.

FIG. 13 is a screenshot illustrating an example interaction with somecomponents of a user interface including multi-colored indicators ofkeyboard finger positions for two hand positions, according to someembodiments.

FIG. 14 is a screenshot illustrating an example interaction with somecomponents of a user interface including multi-colored indicators ofkeyboard finger positions for four hand positions, according to someembodiments.

FIG. 15 is a screenshot illustrating an example interaction with somecomponents of a user interface including a chord-type dropdown menu,according to some embodiments.

FIG. 16 is a screenshot illustrating an example interaction with somecomponents of a user interface including a melody-length dropdown menu,according to some embodiments.

FIG. 17 is a screenshot illustrating an example interaction with somecomponents of a user interface including a melody-type dropdown menu,according to some embodiments.

FIG. 18 is a screenshot illustrating an example interaction with somecomponents of a user interface including a combinations-length dropdownmenu, according to some embodiments.

FIG. 19 is a screenshot illustrating an example interaction with somecomponents of a user interface including a MIDI-instruments dropdownmenu, according to some embodiments.

FIG. 20 is a screenshot illustrating an example interaction with somecomponents of a user interface including listings of chords and melodynotes, according to some embodiments.

FIG. 21 is another screenshot illustrating an example interaction withsome components of a user interface including listings of chords andmelody notes, according to some embodiments.

FIG. 22 is a screenshot illustrating an example interaction with somecomponents of a user interface including listings of rhythm permutationsand combinations, according to some embodiments.

FIG. 23 is a screenshot illustrating an example interaction with somecomponents of a user interface including a step sequencer and rhythmbeats visualizations, according to some embodiments.

FIG. 24 is a screenshot illustrating an example interaction with somecomponents of a user interface including melody permutations with A-Gnotation, according to some embodiments.

FIG. 25 is a screenshot illustrating an example interaction with somecomponents of a user interface including listings of favorite melodiesand favorite chords in integer notation, according to some embodiments.

FIG. 26 is a screenshot illustrating an example interaction with somecomponents of a user interface including melody elements and metadata,according to some embodiments.

FIG. 27 is a screenshot illustrating an example interaction with somecomponents of a user interface including a chord tab, according to someembodiments.

FIG. 28 is another screenshot illustrating an example interaction withsome components of a user interface including a chord tab, according tosome embodiments.

FIG. 29 is a screenshot illustrating an example interaction with somecomponents of a user interface including chord-type dropdown menus,according to some embodiments.

FIG. 30 is a screenshot illustrating an example interaction with somecomponents of a user interface including selected listings of chordpairings in a progression, according to some embodiments.

FIG. 31 is a screenshot illustrating an example interaction with somecomponents of a user interface including a listing of combined chordpairings, according to some embodiments.

FIG. 32 is a screenshot illustrating an example interaction with somecomponents of a user interface including listings of chord permutationsand combinations, according to some embodiments.

FIG. 33 is another screenshot illustrating an example interaction withsome components of a user interface including listings of chordpermutations and combinations, according to some embodiments.

FIG. 34 is a screenshot illustrating an example interaction with somecomponents of a user interface including a listing of favorite chords,pairings, permutations, and combinations, according to some embodiments.

FIG. 35 is a screenshot illustrating an example interaction with somecomponents of a user interface including chord elements and metadata,according to some embodiments.

FIG. 36 is a screenshot illustrating an example interaction with somecomponents of a user interface including an export feature, according tosome embodiments.

FIG. 37 is another screenshot illustrating an example interaction withsome components of a user interface including an export feature,according to some embodiments.

FIG. 38 is a screenshot illustrating an example interaction with somecomponents of a user interface within an independent DAW program,according to some embodiments.

FIG. 39 is a diagram illustrating an example computer system useful forimplementing various embodiments.

In the drawings, like reference numbers generally indicate identical orsimilar elements. Additionally, generally, the left-most digit(s) of areference number identifies the drawing in which the reference numberfirst appears.

DETAILED DESCRIPTION

Provided herein are system, digital audio workstation (DAW), apparatus,device, method, and/or computer-readable storage-medium embodiments,and/or combinations and sub-combinations thereof, for implementing amusic composition aid.

Any of the embodiments provided herein may implement a composer'stoolkit (CTK) as a collection of enhanced processing techniques that maymodel the processes of diffuse thinking and intuition to generategreater ranges of musical possibilities systematically. This modelingand generating may be accomplished, at least in part, by mathematicallyanalyzing specific inputs and systematically generating multiplepossible reusable patterns as outputs.

Advantages of reusability may be understood via other disciplines, suchas software engineering or color theory, to name a few separateexamples. To illustrate the advantages of reusability with color theoryas applied to painting, for example, it is possible to begin withprimary colors of red, blue, and yellow. With these three primary colorelements, it is possible to generate all other colors, such as green,purple, orange, and so on. Creating these secondary colors from scratcheach time would be inefficient.

Instead, such secondary colors may be reused. Similarly, musicalelements and combinations thereof may be generated and reused in wayssimilar to colors on a palette. Rather than composing rhythms andmelodies one piece at a time, for example, it may be possible andadvantageous instead to generate sets of entire rhythms or melodies ascomplete units, then selecting desired units as a whole.

CTK as disclosed herein may package musical elements of any size orlevel of complexity into complete reusable units, allowing a composer towork with each generated element as an entire component instead ofhaving to create those entire components each time. Each musical elementmay be treated as a modular building block. With CTK, composers mayselect unique rhythms and unique melodies as desired and may try themtogether to appreciate the net effect, efficiently facilitating thecomposition process. CTK may be leveraged to expose many musical optionsto let composers select their favorite outputs, and may generateeffectively limitless varieties of musical content.

In some embodiments, CTK may generate musical elements on the fly,without intermediate database storage. Avoiding databases in the courseof such generation may advantageously reduce a memory footprint and/oreconomize on data storage, especially when generating quintillions ofpermutations, combinations, rhythms, melodies, etc., for thousands ofelements simultaneously, for example. Independently of musical elementgeneration per se, separate serializations, files, or database schemesmay be used for storage of data regarding a composer's favorite patternsor styles selected from the elements generated, in some exampleembodiments, without significantly affecting any on-the-fly generationof musical elements.

In some embodiments, CTK may include a code base that may use custommodel-view-controller (MVC) design patterns to create a more robustarchitecture, allowing code to be quickly and seamlessly modified whileretaining a clean and organized structure. The decoupled nature of thiscode may allow some sections of code to be modified without impactingthe rest of the code. Some embodiments are described in further detailvia the examples that follow below.

FIG. 1 is a flowchart illustrating a method 100 for operation of theenhanced music composition techniques described herein, according tosome embodiments. Method 100 may be performed by processing logic thatmay comprise hardware (e.g., circuitry, dedicated logic, programmablelogic, microcode, etc.), software (e.g., instructions executing on aprocessing device), or a combination thereof. Not all steps of method100 may be needed in all cases to perform the enhanced techniquesdisclosed herein. Further, some steps of method 100 may be performedsimultaneously, or in a different order from that shown in FIG. 1, aswill be understood by a person of ordinary skill in the art.

Method 100 shall be described with reference to FIGS. 1 and 39. However,method 100 is not limited only to those example embodiments. The stepsof method 100 may be performed by at least one computer processorcoupled to at least one memory device. An example processor and memorydevice(s) are described below with respect to FIG. 39. In someembodiments, method 100 may be performed by components of computersystem 3900 of FIG. 39, which may further include at least one processor3904 and main memory 3908.

In 102, at least one processor, such as processor 3904, may beconfigured to retrieve a first constraint value, such as via a memory orstorage device (e.g., any of elements 3908-3912 of FIG. 39). The firstconstraint value may be a limit on a size of intermediate datastructures. In some embodiments, the first constraint may be a limit onlist elements that may be generated in 112, as discussed further below.In some embodiments, the first constraint may be a batch limit or slicelimit, e.g., for list slicing, iterable slicing in an iterator function,or equivalent function to allow efficient processing of data subsetsand/or traversal of elements in a container, e.g., in a list, vector,array, matrix, tuple, or similar data structure.

An example of the first constraint includes the stop parameter of theislice function from the itertools functional programming module in thePython Standard Library, for example. The first constraint may serve asa boundary parameter for use with other types of coroutines,subroutines, threads, anonymous functions, higher-order functions,recurrence relations, or other programming techniques, includingfunctional, object-oriented, data-driven, or procedural programming, toname a few non-limiting examples.

The first constraint may be adjusted for a particular system to manageavailable resources, e.g., processor 3904, memory or storage 3908-3912,or time for generating output, for example. In some embodiments, thefirst constraint may be defined by a programmer as a predetermined value(e.g., global constant). In other embodiments, the first constraint maybe a variable that may be modified at runtime, e.g., via input from auser, runtime system metrics (including real-time or near-real-timeupdates of available system resources), command line, API, or otherequivalent means of modifying parameters at runtime.

In 104, processor 3904 may be configured to receive a selection of a setof musical elements. For example, a set of musical elements may be abroad category of components of a musical composition in general, e.g.,rhythm, melody, chords, etc. Narrower subcategories or subsets (e.g.,syncopated rhythms, nota cambiata melodies, minor sixth chords, etc.)may also be considered a selection of musical elements for purposes of104.

The selection of the set of musical elements may occur via input from auser, via semi-automated progression (e.g., a setup wizard), or inputfrom another component, program, or device (e.g., a DAW or modulethereof). The selection may be received by a first module of a userinterface, for example. A user interface or any module thereof mayinclude buttons, a tabbed layout, dropdown menus, text input, commandline, voice input, keyboard shortcuts, other hardware selectors (e.g.,rocker switches, multi-throw switches or knobs, pedals, etc.), such ason dedicated DAW hardware, for example.

Selections may be interactive, such as by a user at runtime, in someembodiments. Additionally, or alternatively, selections may bepredetermined, such as by batch input, for example. Interacting withsuch elements, selections may be made via an input device, e.g.,keyboard, touchscreen, touchpad, trackball, mouse, scroll wheel, knob,switch, pedal, or similar input device, in some embodiments. An exampleimplementation of a user-interface may be based at least in part on aC++ library, such as JUCE, in some embodiments. JUCE or similar C++libraries may interface with program components or libraries written inother languages, such as Python, Ruby, etc., via an applicationprogramming interface (API), foreign function interface (FFI), wrapperlibrary, language binding, shared memory, translation layer, or othernative interface, to name a few non-limiting examples.

In 106, processor 3904 may be configured to accept a second constraintvalue corresponding to the set of musical elements. The secondconstraint value may indicate a subset of the set of musical elements.For example, a user may wish to generate various melodies having sixnotes. A given system may be able to generate melodies of two to sixteennotes, in an embodiment. By accepting a second constraint, such asexactly six notes for a melody, melodies of other lengths may beeliminated, avoiding unnecessary generation of sequences that the usermay not wish to consider.

The second constraint may be a variable that may be modified at runtime,e.g., via a second module of the user interface accepting input from auser, monitoring of runtime system metrics (including real-time ornear-real-time updates of available system resources), command line,API, or other equivalent means of modifying parameters at runtime. Thesecond constraint is also not limited to a single constraint. Forexample, with a melody, the second constraint may specify a number ofnotes and/or a musical interval or chord, further narrowing a subset ofmusical elements to be generated for consideration by the user, in someembodiments.

In 108, processor 3904 may be configured to store the second constraintvalue in the memory, e.g., main memory 3908. Additionally, oralternatively, the storing may store the second constraint value in alonger-term data store, such as any storage devices included in, orattached to, secondary memory 3910. The value of the second constraint,alongside any value of the first constraint where applicable, may beretained and passed as parameters, e.g., call by value, call byreference, call by sharing, etc., or as procedural parameters, in someembodiments. Values may be accepted or otherwise used by one or moremodules or functions, including iterator functions, for example. Thevalue of such a parameter may be received by an iterator function as anargument, as described with respect to 110 below.

In 110, processor 3904 may be configured to invoke a function, such asan iterator function, using at least the second constraint value as anargument. In some embodiments, the first constraint value may also bepassed as an argument when invoking the iterator function. Additionally,or alternatively, the first constraint may be read by the iteratorfunction via a global or system-wide variable or shared memory space, ata time of invocation, execution, or runtime of a given iteratorfunction, for example. Other functionally equivalent methods ofinvocation, e.g., of procedures or functions, with any of the first orsecond constraint values may be contemplated within the scope of thisdisclosure.

In 112, processor 3904 may be configured to generate an output of theiterator function. The output of the iterator function may include atleast part of a subset of the set of musical elements. The subset may bedetermined by the second constraint value, in some embodiments.

For example, the selected set of musical elements may include rhythms ina given meter of regular beats, where a given beat may be strong or weak(e.g., stressed or unstressed beats, on- or off-beats, up- ordown-beats, pulses or rests, etc.). The second constraint may have avalue of [4] (e.g., a list of one element that equals four). In thiscase, the second constraint may limit a resulting output set to rhythmshaving four beats, and where any of the four beats may be stressed orunstressed. Considering only the possible rhythms of four beats, theoutput of the iterator function here may be either stressed orunstressed (two possible values based on the selected set), such thatthe rhythmic possibilities are 2⁴ (2{circumflex over ( )}4), beingsixteen possible orders (permutations) of the beats, allowing repetitionof the same beat sequentially or throughout the sequence, for example.

Accordingly, the output of the iterator function in this example may bethe resultant set of all sixteen permutations of beats, e.g., all fourbeats unstressed, first three beats unstressed with last beat stressed,only the third beat stressed, and so on, through having all four beatsstressed, in this example. The order in which the beats are presentedmay also be varied per system defaults or user preferences, such as by auser-interface setting.

In 114, processor 3904 may be configured to limit a size of the outputof the iterator function, according to the lesser of the firstconstraint value or a transform of the second constraint value, wherethe size of the output is less than or equal to the first constraintvalue. In an example of 112 and 114, the selected set of musicalelements may be melodies in an octave of a diatonic scale, which hasseven distinct tones (e.g., do-re-mi-fa-so-la-ti). The secondconstraint, in this example, may have a value of [4] (e.g., a list ofone element that equals four). In this case, the second constraint maylimit a resulting output set to melodies having four notes, any of whichmay be selected from the seven possible tones in the selected diatonicscale. As permutations allowing repetition, the melodic possibilitiesare 7⁴ (7{circumflex over ( )}4), being 2401 possible orders(permutations) of the notes, selected from seven distinct tones.

In this example, the output of the iterator function may not necessarilybe all 2401 melodic permutations. Subject to the value of the firstconstraint, if the value of the second constraint exceeds the value ofthe first constraint, the actual number of output elements may be thatof the first constraint value, or fewer, in some embodiments. Thus, ifthe value of the first constraint is [1000] (e.g., a list of one elementthat equals 1000), the iterator function may be a generator configuredto return the first 1000 elements of the set of 2401 melodicpermutations of four diatonic notes as output, for example. Thus, inaddition to mathematical generation of (sub)sets of musical elements,other algorithms may be used to streamline generation and/or delivery ofresults, e.g., divide-and-conquer algorithms, segmentation,partitioning, etc.

Additionally, in this case, the iterator function may be called againwith a modified first constraint value, e.g., [1001, 2000] (e.g., a listof two elements, 1001 and 2000), generating the next 1000 elements inthe set of 2401 melodic permutations. Thus, in some embodiments, thefirst constraint value may be a list comprehension, set comprehension,or set-builder notation value enumerating or specifying domain for asubset of a set of musical elements bounded by the second constraintvalue. As described above, the second constraint value, like the firstconstraint value, may be a list, vector, array, matrix, tuple, orsimilar data structure, for example, and the first constraint value maybe a slice limit or batch limit.

Thus, the output of the iterator function may be kept at a manageablelevel within physical constraints of hardware with limited computingpower and storage capacity (see 116 below). For larger sets or subsetsof musical elements, sheer data volume of representations (e.g., integernotation, letter notation, etc.), may lead to data sets that are toolarge to store in memory of a given computer system (e.g., main memory3908 of computer system 3900).

In 116, processor 3904 may be configured to store the output of theiterator function in the memory. In some embodiments, the output of theiterator function may not fit in the memory without performing 114 asdescribed above. As also described further above, the value of the firstconstraint may be adjusted manually or automatically depending on systemhardware constraints, to ensure, for a given system specification and/oruser preference, that the output of the iterator function may safely bestored in a given memory (e.g., main memory 3908 and/or secondary memory3910 of computer system 3900).

For example, if selecting melodies of two to sixteen notes on achromatic scale of twelve distinct tones, the second constraint valuemay be, in some embodiments, an enumerated list of [2, 3, 4, 5, 6, 7, 8,9, 10, 11, 12, 13, 14, 15, 16], or equivalent programmaticrepresentation, comprehension, specification, etc. Thus, the totalnumber of possible melodic permutations (Σ_(n=2) ¹⁶ 12^(n)) may reachmore than two-hundred quadrillion possibilities. Even efficientrepresentations of total output sets may expand to many terabytes orpetabytes of data, in some cases, even with compression. These datarepresentations alone may exceed overall available storage capacity ofmany computer systems (e.g., secondary memory 3910 including anyremovable storage 3918 or 3922), according to some embodiments.

Without the first constraint (e.g., batch limit or slice limit) incombination with an iterator function such as a coroutine or generator,sizes of the resultant data sets may push the envelope of complex,high-end computing systems, becoming “big data” problems impractical formost independent music composers to provision for, let alone forattention spans of human musicians attempting to test many differentcomposition ideas while avoiding fatigue. Combined with output ofrendered elements (see 118 below), size of resultant output data maygrow several times more without appropriate constraint values. At leastas a result of 114, and depending on an appropriate value of the firstconstraint for a given computer system 3900, resultant output sets ofmusical elements may be reasonably and safely stored in a given memory(e.g., main memory 3908 and/or secondary memory 3910 of computer system3900), in some embodiments.

In 118, processor 3904 may be configured to render the output of theiterator function via a third module of the user interface. In someembodiments, the output of the iteration function may be stored (per116) in a memory or storage, where the output may be a datarepresentation of a musical element (e.g., rhythm, melody, chord, or acombination thereof). The representation may include, constitute, or betranslated to, messages or instructions for audio playback, such as viaa standard Musical Instrument Digital Interface (MIDI), to name onenon-limiting example.

The representation may be retrieved by a rendering engine or otherprogram, function, module, driver, device, DAW, or comparable mechanismthat may be configured to render musical output audibly (sonification)and/or visually (visualization). Such sonification or visualization maybe rendered and/or controlled via the third module of the userinterface, which may be a physical or virtual button, knob, slider,keyboard, frame, scope, window, monitor, etc., in some embodiments. Arendering engine may include or connect to an audio adapter or videoadapter, for example.

Sonification may be realized via at least one digital-to-analogconverters (D/A, D2A, DAC), audio sequencer, synthesizer, mixer, DAW,MIDI controller, or combination thereof, among other comparable devices,which may further be communicatively coupled to at least one loudspeakeror loudspeaker array, for example. Visualization may be a synchronoustransform of an audio signal converted to image(s) or a video sequence,for example. Additionally, or alternatively, in some embodiments,visualization may include a display of musical notation (e.g., score,tablature, MIDI message) or graphical representation thereof.

Any rendering may be quickly toggled across different musical elementsof the output of the iterator function, such as via the third module ofthe user interface, or via a similar module, in some embodiments. Someexamples may include hotkeys or click-play-click-play paradigms that mayallow a user to advance through musical elements within a given set orsubset of iterator function output, in a way that is quick andefficient, allowing systematic coverage of elements that have not yetbeen rendered (e.g., sonified or visualized for consideration by theuser). This interaction may continue, in some use cases, until a userhas found enough musical elements to be satisfactory, for example.

In some embodiments, metadata may be associated with any given elementor rendering. Such metadata may include an indication of whether a givenmusical element of the output has been rendered, a rating, an elementdescriptor, a component descriptor, or a mood descriptor. Such metadatamay further include associations with other musical elements, e.g.,attaching at least one chord to a melody and/or attaching at least onemelody to a rhythm, etc.

Additionally, these metadata may also allow easy retrieval in thefuture, e.g., for favorite elements, highly-rated elements, elementsthat evoke a specific subjective mood or reaction in the user, etc.Additional descriptions of the CTK user interface are described furtherbelow. A composer may be able to input a new tag or descriptor withinthe Favorites portion of CTK. Each rhythm, chord, melody, lyric,instrumentation, or a combination thereof, may then be tagged with amood or description, for example.

These metadata may allow systematic review of output elements by a userfor the first time considering the elements in a given compositionproject. Additionally, indications of whether musical elements have beenrendered or considered may be compiled into a history, along with groupsof favorites, ratings, moods, or other descriptors or metadata tags, forexample. Retrieval of history items may be performed in batches of apredetermined size, such as for memory efficiency, according to someembodiments.

A composer may be able to use their own vocabulary to describe how theyperceive these musical elements. For example, if a composer may wish toclassify a chord as subjectively sounding dark and brooding, the usermay tag and search for all chords that may fit this description, in someembodiments. Music may evoke different emotions, for which composers maywant a way to describe consistently for later recall, categorization,and grouping. For example, film score composers may be able to searchquickly for the musical elements that evoke a specific mood forcorresponding scenes of a screenplay.

Referring to the CTK user interface, some embodiments of CTK may includea rhythm tab that may use integer partitions to create a rhythmicsequence. Permutations on the resulting sequence may reveal, within thefirst or second constraint values, rhythmic variations that arepossible. Shifting or rotating the sequence may aid this process aswell.

FIG. 2 is a screenshot illustrating an example interaction with somecomponents of a user interface including a rhythm tab, according to someembodiments. FIG. 3 is another screenshot illustrating an exampleinteraction with some components of a user interface including a rhythmtab, according to some embodiments, in an alternative arrangement fromthat of FIG. 2.

Among other user-interface elements, FIG. 2 shows a display of rhythmsusing a graphical representation of stressed and unstressed beats in arhythm element. In some embodiments, the graphical representation may beglyphs in a font, for example. By contrast, FIG. 3 shows a display ofvarious rhythms in integer notation, as well as a visual display usingcheckboxes, in an embodiment separate from that of FIG. 2. In someembodiments, user-interface modules of FIG. 2 and FIG. 3 may be combinedin the same embodiment, as shown in FIG. 23 further below, for example.

For example, if a composer wants a sequence of 16 beats, a partition ofbeats may end up being 1 1 1 1 1 1 2 2 3 3=16, in decimal integernotation. From here a composer may convert these integers into acorresponding binary form where the partition values of n begin with astressed beat (‘1’) and are followed by n−1 unstressed beats (‘0’), insome embodiments, becoming 1 1 1 1 1 1 1 0 1 0 1 0 0 1 0 0. This mayalso be viewed and controlled with a sequence of checkboxes such as inFIG. 4.

FIG. 4 is a screenshot illustrating an example interaction with somecomponents of a user interface including a checkbox visualization ofbeats, according to some embodiments. The visualization of FIG. 4 is analternative embodiment of the graphical representation of stressed andunstressed beats shown in FIG. 2. Similarly, the checkbox representationmay be based on rendered text implemented by glyphs in a font.

This visual display (in either or both of FIG. 2 or 4) may represent astep sequencer. If there is a check in the step sequencer then it meansa composer may play the rhythm at that point in time. If there is nocheck in the step sequencer then, in some embodiments, nothing isplayed. In some embodiments, a specific default value may be specifiedfor unchecked boxes, including an unstressed beat, for example.

FIG. 5 is a screenshot illustrating an example interaction with somecomponents of a user interface including a rhythm-length dropdown menu,according to some embodiments. A composer may select how long they wantthe rhythmic sequence to be. In this particular example, the number ofbeats and tempo/duration of beats (or triplets) may be set to determinean overall length of the rhythmic sequence. The number of beats in arhythmic sequence, according to an embodiment, may range from 3 beats to16 beats. As soon as the composer selects a Rhythm Length, the Rhythmslist box may be populated with all the possible integer partitions forthat length.

FIG. 6 is a screenshot illustrating an example interaction with somecomponents of a user interface including rhythm shift buttons, accordingto some embodiments.

The Left (−) button may shift or rotate the rhythmic sequence to theleft. The Right (+) button may shift or rotate the rhythmic sequence tothe right. Shift functionality and/or rotate functionality may allow thecomposer to discover more rhythmic variations.

The Add To Favorites button lets the composer add the current binaryrhythm sequence (as seen in the Visual section) to the Favorites listbox. This may let the composer store a given favorite rhythmic sequencein a list box if that sequence does not already exist in the list box. ANext Batch button (not shown) may be selected to find additionaldifferent permutations of a given rhythm length, for example.

When a composer adds a favorite rhythm to the list box, the binaryrhythm sequence may be converted into an integer partition sequence, insome embodiments.

FIG. 7 is a screenshot illustrating an example interaction with somecomponents of a user interface for a rhythm permutation listing,according to some embodiments.

After the integer partition is selected in the Rhythms list box, thecomposer may hit the Next Batch button to calculate permutations of thatinteger partition sequence. The calculated permutations may then bedisplayed in accordance with the composer's preferences.

In some embodiments, due to efficiency requirements, or to save memory,to name a few possible system constraints, a limited number ofpermutations (e.g., up to a thousand) may be generated at a time. Acomposer may then hit the Next Batch button again to generate the nextset of permutations.

FIG. 8 is a screenshot illustrating an example interaction with somecomponents of a user interface including dropdown menus for beats andMIDI instruments, according to some embodiments.

A composer may play a rhythmic sequence using, in some embodiments, 128different MIDI instruments, for example. Instruments may be changed inthe first drop-down menu, to name an example user-interface element forselection.

The second drop down may let the composer select how they want therhythmic sequence to be interpreted in terms of its note value, in someembodiments. For example, selecting “16th” may interpret each beat as a16th note.

The Play button may play the currently selected rhythmic sequence in theVisual section. Audio playback may be generated via MIDI, according tosome embodiments.

The Play button shown in FIG. 8 is an example providing an interfaceconforming to a click-play-click-play paradigm that may allow a user toadvance through musical elements within a given set or subset ofiterator function output (e.g., from method 100), in a way that is quickand efficient.

FIG. 9 is a screenshot illustrating an example interaction with somecomponents of a user interface including a favorite rhythms listing,according to some embodiments.

The Favorites list box may store all the rhythmic sequences that thecomposer has selected, for example. In some embodiments, duplicatesequences may be disallowed or eliminated from this list box, such asvia a deduplication function, for example.

When a composer selects a favorite rhythmic integer partition, theVisual section may be automatically updated with the selected rhythm, insome embodiments. A composer may play their favorite rhythms byselecting a rhythm from the Favorites section and hitting Play in theMIDI section. A composer may also delete a rhythm from the Favoriteslist box.

Separately, Table 1 shows a non-limiting range of possibilities for oneparticular example configuration. For example, selecting a rhythm lengthof 16 beats may allow for nearly 21 trillion different rhythms in someconfigurations. Allowing a composer to sort through these efficientlyand select favorite rhythms as desired may present significantadvantages for creativity and productivity.

TABLE 1 Rhythm Length Range: 3 to 16 beats Partition Range: 3 to 231partitions Max MIDI instruments: 128 total instruments Note ValuePlayback: Quarter, 8th, 8th triplet, 16th, 16th triplet, 32nd, 32ndtriplet Rhythmic Range: 3! to 16! (6 to 20,922,789,888,000) differentrhythms

FIG. 10 is a screenshot illustrating an example interaction with somecomponents of a user interface including rhythm elements and metadata,according to some embodiments.

In some embodiments, metadata may be associated with any given elementor rendering. Such metadata may include an indication of whether a givenmusical element of the output has been rendered, a rating, an elementdescriptor, a component descriptor, or a mood descriptor. These metadatamay allow systematic review of output elements by a user for the firsttime considering the elements in a given composition project.Additionally, these metadata may also allow easy retrieval in thefuture, e.g., for favorite elements, highly-rated elements, elementsthat evoke a specific subjective mood or reaction in the user, etc. Insome embodiments, metadata may include associations with other musicalelements, for example.

FIG. 11 is a screenshot illustrating an example interaction with somecomponents of a user interface including a melody tab, according to someembodiments.

The melody tab may generate chords, in some embodiments, including everychord that may exist for a specified set of notes or within a specifiedpitch range. Once a chord is selected, CTK may generate all the melodynotes that work with that chord.

Instead of calculating all the chords that come from a scale, in someembodiments, CTK may start with the chord and find all the possible notesequences that may work with that chord. From here, CTK may beconfigured to calculate up to every permutation and combination possiblefor a melody note sequence. CTK may then take these sequences and assignup to every possible rhythm of up to the selected maximum length. Acomposer may select desired sequences from results presented by CTK viaa user interface.

FIG. 12 is a screenshot illustrating an example interaction with somecomponents of a user interface including an integer-annotated keyboard,according to some embodiments.

Notes (e.g., C, C#/D♭, D, D#/E♭, E, F, F#/G♭, G, G#/A♭, A, A#/B♭, B) maybe represented by numbers, in this case integers, in some embodiments.Besides integer partitions and/or letter notes (A-G), other notationschemes may be used to represent specific musical notes, including forvarious other tonal or atonal arrangements. The figure below showsequivalent piano keys corresponding to the note that each number mayrepresent, in the example embodiment shown in FIG. 12.

FIG. 13 is a screenshot illustrating an example interaction with somecomponents of a user interface including multi-colored indicators ofkeyboard finger positions for two hand positions, according to someembodiments.

The two hand positions as shown in FIG. 13 may be highlighted with colorfills, markers, or other symbols, and may further have a unique colorfor each hand position. The two hand positions shown may be sequential,such as for a chord progression, or simultaneous, such as may bepossible for one keyboardist in a solo and/or two keyboardists in aduet. The hand positions shown are not limited only to arrangementsplayable by human keyboardists, but may also serve as an aid for musictheory in compositions for computerized or electronic music not readilyplayable by human keyboardists.

FIG. 14 is a screenshot illustrating an example interaction with somecomponents of a user interface including multi-colored indicators ofkeyboard finger positions for four hand positions, according to someembodiments.

The four hand positions as shown in FIG. 14 may be highlighted withcolor fills, markers, or other symbols, and may further have a uniquecolor for each hand position, or for each possible human player, forexample. The four hand positions shown may be sequential, such as for achord progression, or simultaneous, such as may be possible for twokeyboardists in a duet. The hand positions shown are not limited only toarrangements playable by human keyboardists, but may also serve as anaid for music theory in compositions for computerized or electronicmusic not readily playable by human keyboardists.

Thus, for the some portions of CTK, e.g., handling chords and/ormelodies, a graphical user-interface element may show a graphic of akeyboard with the notes highlighted. This may help to identify chordsvisually without having to rely on written notation (e.g., integer,letter, solmization, etc.).

FIG. 15 is a screenshot illustrating an example interaction with somecomponents of a user interface including a chord-type dropdown menu,according to some embodiments.

A composer may select diads (2-note chords, also referred to asintervals) up to dodecads (12-note chords). When a chord type isselected, the Chords list box may show up to every n-note chord possiblewithin a specified range. For example, if triads are selected, thenvarious 3-note chords in a range may be listed.

FIG. 16 is a screenshot illustrating an example interaction with somecomponents of a user interface including a melody-length dropdown menu,according to some embodiments.

When a composer selects a chord, the composer may want to generate anarbitrary number (n) of melody notes based on the chord. This may bereflected in the Melody Notes list box.

FIG. 17 is a screenshot illustrating an example interaction with somecomponents of a user interface including a melody-type dropdown menu,according to some embodiments.

The melody-type dropdown menu may provide a composer with an option toselect whether or not the notes generated are desirable to the composerwith respect to the chord. A composer may want this option, becauseadding notes that are not contained in the chord may create dissonance,in some cases. This selection feature may keep both tonal and atonaloptions open to the composer, in some embodiments. This may be reflectedin the Melody Notes list box (see FIGS. 11, 20, and 21 herein).

FIG. 18 is a screenshot illustrating an example interaction with somecomponents of a user interface including a combinations-length dropdownmenu, according to some embodiments.

A composer may generate a melody note sequence combination of anarbitrary length n. For example, if a composer chooses a combinationlength of 8 on a 4-note melody (0 1 2 6 8) sequence, then all thepossible combinations that are 8 notes long and contain only 4 of thenotes (0 0 0 1 2 8 8 8) may get displayed in the Combinations list box,in some embodiments.

Combinations may let a composer repeat certain notes in the melody, insome embodiments. This may make a composer's selected note sequencessound more musical to the composer, for example, because melody notes inthe real world may repeat.

FIG. 19 is a screenshot illustrating an example interaction with somecomponents of a user interface including a MIDI-instruments dropdownmenu, according to some embodiments.

A composer may play both chords and melody sequences using, for example,128 different MIDI instruments, in some embodiments. Instruments may bechanged in a drop-down menu, to name one possible GUI element forselection, among other possible options.

FIG. 20 is a screenshot illustrating an example interaction with somecomponents of a user interface including listings of chords and melodynotes, according to some embodiments.

When a composer selects a chord from the Chords list box, the MelodyNotes list box may get populated with all the notes that the composerindicated as being suitable or unsuitable to combine with the selectedchord. This may be stored persistently, such as in a database,serialization, file, or other type of data store. This may facilitate acomposer later finding which notes are favored by the composer with thesame or similar chords, for example.

The Play Chord button may play the currently selected chord. The PlayMelody Notes button may play both the currently selected chord and themelody note sequence at the same time. This may let composers hear howthe melody sounds over the chord. Audio playback may be generated viaMIDI.

The Add To Favorites button may allow a composer add their favoritechord or melody note sequence to the Favorites section.

FIG. 21 is another screenshot illustrating an example interaction withsome components of a user interface including listings of chords andmelody notes, according to some embodiments.

FIG. 22 is a screenshot illustrating an example interaction with somecomponents of a user interface including listings of rhythm permutationsand combinations, according to some embodiments.

In some embodiments, the list boxes as shown in FIG. 22 may be employed,in no particular order, to name a few non-limiting examples:Permutations, Combinations, Rhythms, Rhythmic Permutations, and RhythmicRotations. Any other order or elements may be presented here.

This section lets a composer perform controlled experiments on findingthe best melody and rhythm combination as well as showing all thepossible ways to play a selected melody sequence. Once a melody notesequence is selected, a composer may use the Next Batch button togenerate all the permutations and combinations on that sequence.

The Permutation Rhythms and Combination Rhythms buttons may generate allthe rhythms that may be played with the n number of notes in each melodysequence. Once a permutation or combination rhythm is generated, acomposer may select a rhythm in the Rhythms list box and all therotations/shifting may be performed on the rhythmic sequence. This mayassist a composer in finding additional rhythmic variations.

The Play buttons may play all melody permutations (with chord), melodycombinations (single notes), melody permutations with rhythm, and melodycombinations with rhythm.

The drop-down under the Rhythm Rotations list box lets the composerselect how they want the rhythmic sequence to be interpreted in terms ofits note value. For example, selecting “16th” may interpret each beat asa 16th note.

The Add To Favorites button lets a composer add their favorite chord,melody sequence, and permutation and combination melody note sequencesto the Favorites section.

FIG. 23 is a screenshot illustrating an example interaction with somecomponents of a user interface including a step sequencer and rhythmbeats visualizations, according to some embodiments.

The Favorites section stores entries and/or listings of a givencomposer's favorite chords, melody notes, and melodicpermutations/combinations. In some embodiments, such stored entriesand/or listings may be deduplicated.

A composer may play their favorite chords or melodies by selecting asequence from the Favorites section and hitting the Play button.

A composer may also delete any chord or melody sequence from theFavorites list boxes.

In an example embodiment, the first list box may contain favorite chordsselected by a composer. The second list box may contain the composer'sfavorite melody notes obtained from a specific chord. The third list boxmay contain melody notes that were generated using permutations andcombinations. Any other order or combination of list boxes or elementsmay be used here.

As shown by way of non-limiting examples above, the melody tab may beused to generate combinations and/or permutations of notes within aselected chord, for any chord. At a different level, the chordprogression tab (described below) may be used to generate chordprogressions based on combinations and/or permutations in a similar way.

Separately, Table 2 shows a non-limiting range of possibilities for oneparticular example configuration. For example, selecting a rhythm lengthof 12 beats as a second constraint value (see method 100) may allow fornearly a half-billion different rhythms in some configurations. Melodiesranging up to 12 notes long in a 12-note scale may allow for nearly ahalf-billion combinations of notes. Rearranging the order of the notesin these possible melodies allows for more permutations by orders ofmagnitude, for nearly 185 quadrillion unique melodies.

TABLE 2 Chord Types: Diads (2 notes), Triads (3 notes), Tetrads (4notes), Pentads (5 notes), Hexads (6 notes), Heptads (7 notes), Octads(8 notes), Nonads (9 notes), Decads (10 notes), Undecads (11 notes),Dodecads (12 notes) Max Chords Possible: Diads (66), Triads (220),Tetrads (495), Pentads (792), (in a 12-note chromatic scale) Hexads(924), Heptads (792), Octads (495), Nonads (220), Decads (66), Undecads(12), Dodecads (1) Total = 4083 Possible Chords Number of Melody Notes 2to 12 notes Range: Type of Melody Notes: Consonant or DissonantCombinations Length 2 to 16 notes Range: Max MIDI instruments: 128 totalinstruments Combinations Range: 2! to 12! (up to 479,001,600) notecombinations Permutations Range: 2² to 12¹⁶ (up to184,884,258,895,036,416) different (Number of Melody Notes (m) melodiesto the power of Combinations Length (c) = (m^(C))) Rhythm Length Range:2 to 16 beats Partition Range: 2 to 77 partitions Note Value Playback:Quarter, 8th, 8th triplet, 16th, 16th triplet, 32nd, 32nd tripletRhythmic Range Possibility: 2! = 2 to 12! = 479,001,600 differentrhythms

FIG. 24 is a screenshot illustrating an example interaction with somecomponents of a user interface including melody permutations with A-Gnotation, according to some embodiments. In some embodiments, a user maybe provided with the option to change how all the chords and melodiesare displayed. A composer may display notes in letter notation (A-G),solmization (e.g., do, re, mi, etc.), roman numeral analysis, or integernotation (0-11), to name a few non-limiting examples.

FIG. 25 is a screenshot illustrating an example interaction with somecomponents of a user interface including listings of favorite melodiesand favorite chords in integer notation, according to some embodiments.

The chord progression tab may also generate up to every chord that mayexist for a selected range of notes, pitches, octaves, or type ofprogression selected (e.g., perfect fifths, circle progressions, etc.).Once a chord is selected, a composer may try that chord against all theother chords. The composer may then combine, for example, two chordpairings to form a 4-chord progression, in some embodiments. From here acomposer may calculate every permutation and combination possible forthe chord progression. The composer may then take these chordprogressions and assign a rhythm to it.

FIG. 26 is a screenshot illustrating an example interaction with somecomponents of a user interface including melody elements and metadata,according to some embodiments.

Selecting a type from the top left drop-down may generates chords up toall possible chords of that type for a desired range and/or progression.These chords appear in the Chord Pairings I & II section shown in theFigure below. Selecting a type from the bottom left drop down may alsogenerate all the possible chords of the selected type and/or from aselected range of notes, pitches, and/or octaves.

These chords may be paired against a single chord in the Chord PairingsI & II section. In some embodiments, other numbers of chords may bematched. This process may be repeated for the top right and bottom rightdrop-down menus. This process may be executed to create first and secondchord pairings.

FIG. 27 is a screenshot illustrating an example interaction with somecomponents of a user interface including a chord tab, according to someembodiments.

The chord progression tab may also generate up to every chord that mayexist for a selected range of notes, pitches, octaves, or type ofprogression selected (e.g., perfect fifths, circle progressions, etc.).Once a chord is selected, a composer may try that chord against all theother chords.

The composer may then combine, for example, two chord pairings to form a4-chord progression, in some embodiments. From here a composer maycalculate every permutation and combination possible for the chordprogression. The composer may then take these chord progressions andassign a rhythm to it.

FIG. 28 is another screenshot illustrating an example interaction withsome components of a user interface including a chord tab, according tosome embodiments.

FIG. 29 is a screenshot illustrating an example interaction with somecomponents of a user interface including chord-type dropdown menus,according to some embodiments.

Selecting a type from the top left drop-down may generates chords up toall possible chords of that type for a desired range and/or progression.These chords appear in the Chord Pairings I & II section shown in theFigure below. Selecting a type from the bottom left drop down may alsogenerate all the possible chords of the selected type and/or from aselected range of notes, pitches, and/or octaves.

These chords may be paired against a single chord in the Chord PairingsI & II section. In some embodiments, other numbers of chords may bematched. This process may be repeated for the top right and bottom rightdrop-down menus. This process may be executed to create first and secondchord pairings.

FIG. 30 is a screenshot illustrating an example interaction with somecomponents of a user interface including selected listings of chordpairings in a progression, according to some embodiments.

Selecting a chord from the first list box may pair that chord againstany or all other chord types of a composer's choice of chords and/orprogressions. This process repeats for the second pairing. Once bothpairings are chosen, a composer may combine these pairings into, in someembodiments, a 4-chord progression by clicking the Combine Pairingsbutton. Its important to know that if a composer may want to update thesecond list box with a different chord type, then they may change thechord type in the drop down and then select the chord again in the firstlist box.

A composer may use the Play button to play a chord or a chord pairing atany time. The Add To Favorites button lets a composer add their favoritechord(s) or chord pairing(s) to the Favorites section.

FIG. 31 is a screenshot illustrating an example interaction with somecomponents of a user interface including a listing of combined chordpairings, according to some embodiments.

Once a composer has a combined pairing, a composer may use the Playbutton to hear the chord progression played back. A composer may alsoadd a combined pairing to the Favorites section by clicking the Add ToFavorites button. If the composer decides against using the combinedpairing, the composer may delete it from the Combined Pairings list boxby clicking the Delete Pairing button.

FIG. 32 is a screenshot illustrating an example interaction with somecomponents of a user interface including listings of chord permutationsand combinations, according to some embodiments.

In some embodiments, the list boxes as shown in FIG. 33 may be employed,in no particular order, to name a few non-limiting examples:Permutations, Combinations, Rhythms, Rhythmic Permutations, and RhythmicRotations. Any other order or elements or choices may be presented here.

This section may let a composer perform controlled experiments onfinding the best chord and rhythm combination as well as showingpossible ways to play a selected chord progression.

Once a combined chord is selected, a composer may use the Next Batchbutton to generate permutations and combinations on that chord.

The Permutation Rhythms and Combination Rhythms buttons may generaterhythms that may be played with an arbitrary number (n) of chords ineach progression.

Once a permutation or combination rhythm is generated, a composer mayselect a rhythm in the Rhythms list box and all the rotations/shiftingmay be performed on the rhythmic sequence. This may assist a composer infinding additional rhythmic variations.

The Play buttons may play all chord permutations, chord combinations,chord permutations with rhythm, and chord combinations with rhythm.

The drop-down under the Rhythm Rotations list box lets the composerselect how they want the rhythmic sequence to be interpreted in terms ofits note value. For example, selecting “16th” may cause the tool tointerpret each beat as a 16th note.

The Add To Favorites button lets a composer add their favorite chord,chord pairing, and permutation and combination of the chord pairings tothe Favorites section.

FIG. 33 is another screenshot illustrating an example interaction withsome components of a user interface including listings of chordpermutations and combinations, according to some embodiments.

FIG. 34 is a screenshot illustrating an example interaction with somecomponents of a user interface including a listing of favorite chords,pairings, permutations, and combinations, according to some embodiments.

The Favorites list boxes may be used to store and/or display thecomposer's favorite chords, chord pairings, as well as permutations andcombinations of chords. In some embodiments, such stored entries and/orlistings may be deduplicated.

A composer may play their favorite chords or pairings by selecting asequence from the Favorites section and hitting the Play button.

A composer may also delete any chord or chord pairing from the Favoritessection.

Table 3 shows an non-limiting range of possibilities for one particularexample configuration. For example, selecting an 8-note combinationslength and combining four such chords may allow for over 65 thousanddifferent chord pairings in some configurations. Allowing a composer tosort through these efficiently and select favorite rhythms as desiredmay present significant advantages for creativity and productivity.

TABLE 3 Chord Types: Diads (2 notes), Triads (3 notes), Tetrads (4notes), Pentads (5 notes), Hexads (6 notes), Heptads (7 notes), Octads(8 notes), Nonads (9 notes), Decads (10 notes), Undecads (11 notes),Dodecads (12 notes) Chords Range: Diads (66), Triads (220), Tetrads(495), Pentads (792), (in a 12-note chromatic scale) Hexads (924),Heptads (792), Octads (495), Nonads (220), Decads (66), Undecads (12),Dodecads (1) Total = 4,083 different chords Combinations Length Range: 8notes Combined Pairings Range: 4 chords Combinations Range: 4! = 24possible chord arrangements Permutations Range: 4⁸ = 65,536 differentchord arrangements (Number of chords (m) to the power of CombinationsLength (c) = (m^(C))) Rhythm Length Range: 16 beats Partition Range: 22to 34 partitions Note Value Playback: Quarter, 8th, 8th triplet, 16th,16th triplet, 32nd, 32nd triplet Rhythmic Range Possibility: 4! = 24 to8! = 40,320 possible rhythms

FIG. 35 is a screenshot illustrating an example interaction with somecomponents of a user interface including chord elements and metadata,according to some embodiments.

In some embodiments, metadata may be associated with any given elementor rendering. Such metadata may include an indication of whether a givenmusical element of the output has been rendered, a rating, an elementdescriptor, a component descriptor, or a mood descriptor. These metadatamay allow systematic review of output elements by a user for the firsttime considering the elements in a given composition project.Additionally, these metadata may also allow easy retrieval in thefuture, e.g., for favorite elements, highly-rated elements, elementsthat evoke a specific subjective mood or reaction in the user, etc. Insome embodiments, metadata may include associations with other musicalelements, for example.

FIG. 36 is a screenshot illustrating an example interaction with somecomponents of a user interface including an export feature, according tosome embodiments.

In embodiments where a composer may have to type the patterns into aDAW, mixer, synthesizer, or sequencer, for example, other time-savingmeasures may be helpful. To save time, CTK may be able to create abutton to export rhythms, chords, melodies, and so on via MIDI.

The composer may then import the MIDI output from CTK into the DAW orsequencer, and may manually edit the MIDI notes or patterns along theway, such as for fine-tuning a final version or intermediate sequence,in some embodiments. Additionally, in some embodiments, multipleiterations of patterns generated by CTK may chained together after theyare exported and/or edited. These sequences of CTK output, e.g., in theform of MIDI data, may be sent to a virtual instrument to achieve morerealistic playback, for example.

In some embodiments, a user may be presented with options to export orsave selected music elements in a variety of formats, such as standardMIDI files, other MIDI file formats, Virtual Studio Technology (VST), orother industry standards, which may facilitate work with a third-partyDAW apparatus or software, for example.

For export or playback in CTK, MIDI octaves may be selectable, in someembodiments. By allowing the user to select a lower octave for MIDIplayback, the melody tab may be used to create melodies in differenttonal ranges, e.g., bass melodies, harmony, countermelodies, and othersimilar patterns, for example.

FIG. 37 is another screenshot illustrating an example interaction withsome components of a user interface including an export feature,according to some embodiments.

Additionally, or alternatively, further embodiments may include MIDIout-routing to instruments, not only to MIDI files of various formats.Various MIDI instruments may be chosen and used to render generatedmusical elements at runtime without needing to export to a MIDI file,for example.

FIG. 38 is a screenshot illustrating an example interaction with somecomponents of a user interface within an independent DAW program,according to some embodiments.

In some embodiments, 16 beats may be designated as a cap for the rhythmlength to keep the musical elements lean. Generally, the higher thenumber of beats, the less “musical” a rhythm may become. Once somefundamental pieces are acquired, composers may combine them to formlarger pieces of music. This same reasoning was applied when using2-chord pairings and 4-chord combined pairings. Once a composer has theelements built, the composer may mix and match the elements in any waythe composer may want.

A separate tab for arpeggios may be included in some embodiments.Arpeggios may be treated as broken-down chords, which may be furthersequenced according to different permutations depending on the number ofunique notes in each chord.

In addition to keyboard visualizations (see, e.g., FIGS. 2, 13, and 14),CTK, or an associated DAW, may be configured to show a piano-rollvisualization, for further assistance with composition absent knowledgeof notation or traditional music theory, for example. With support forthese features and others, an example of a CTK-compatible DAW programincludes FL Studio by Image-Line Software. In some embodiments, CTK mayinterface with or integrate with FL Studio, such as in the form of aplugin, script, file, library, or a combination thereof, for example. Insome embodiments, CTK may be a standalone program. In furtherembodiments, CTK may be integrated in a standalone apparatus, such asdedicated DAW hardware, for example.

CTK may generate up to all the possible chord inversions in the melodytab. To do this, a composer may match up the chord type to the equalnumber of melody notes, select a chord in the Chords list box, selectthe chord again in the Melody Notes list box, then hit the Next Batchbutton under the Permutations list box. For example, for a triad (3notes), a composer may select 3 in the Number of Melody Notes drop-downand select a chord.

CTK may further include any of the following features and enhancements,to name a few non-limiting examples:

In some embodiments, CTK may further include a lyrics tab (not shown)configured to calculate possible words and syllables that may fit withina binary rhythm sequence. For example, in the sequence 1 0 0 1 0 1 0,CTK may find words or syllables, such as in a specific dictionary, thatmay fit 100, 10, and 10 (3, 2, and 2, in decimal rhythm integernotation). The composer may be able to swap out each word until theperfect lyric combination is obtained. This tab may also contain atraditional dictionary, rhyming dictionary, and thesaurus for quickreference.

Rappers may benefit heavily from the lyrics tab, because vocals maydouble as rhythmic tools, in some genres of music including rap music.The lyrics tab may thus enable rappers to spot rhythms they like andassociate words to those rhythms instantly.

A composer may be able to select one instrument and pair it against allother instruments. Arrangers and orchestrators may use this to discoverevery combination of instruments possible. This tab may also let thecomposer add new instruments to the list and repeat the pairing process.

In some embodiments, CTK may further include a voice-leading tab (notshown). In a case of a voice-leading tab, CTK may be configured to passa chord progression and then automatically calculate a smooth voice whentransitioning from chord to chord. This may have an option to avoidusing block chords or other progressions that may sound jarring.

The advantages of CTK's enhanced techniques as described herein, andother advantages and benefits of implementing and using CTK, shall beapparent to persons of ordinary skill in the art. Among various uses,CTK may be used systematically and efficiently as a countermeasureagainst writer's block for a music composer (composer's block), as CTKmay be configured to generate a variety of possible musical elementsthat a user may test. The enhanced techniques, as described herein,allow for a wide variety of elements generated by CTK and efficientlyconsidered and evaluated by users, saving considerable time overtraditional composition methods, even including modern DAW uses.

An added benefit of CTK's metadata as described above is that, withindications of which output elements have been rendered, considered, orevaluated (or conversely, which elements have not), users may cover manypossibilities without retracing their steps. While existing tools togenerate chords, for example, are limited only to simple rules of musictheory and may provide no guidance for possibilities already considered,CTK may open a virtually limitless array of possible music elements, andmay efficiently track how a user considers those possibilities, allowingthe user to cover significantly more options in a similar span of time.

Even if conventional tools could theoretically generate all thesepossibilities, the results would be practically unusable for independentcomposers, not only due to enormous computing and storage requirementsto process and store petabytes of data, in real time, but also for anindividual user to consider and process the output efficiently. Bycontrast, using the enhanced techniques described herein, CTK mayefficiently provide a composer with a window into a seemingly infinitemusical world, a slice at a time.

CTK also may facilitate music education, reducing time needed tocomprehend music theory, quickly enabling a wide array of specific typesof musical element sets and subsets that can be generated quickly usingiterator functions and rendered realistically, using nearly any virtualinstrument sonification or visualization tools, in some embodiments.This facility lowers barriers to entry for potential users who may knownothing about music theory but who may be curious about musiccomposition, for example. Even for experienced composers, CTK may notneed to do all the work, but may spark the composer's own creativityenough to open new creative territory, genres, and unconventional soundpatterns pleasing to human listeners, none of which could be easilyautomated. Additionally, musical elements, metadata, and any renderings,may be independently and selectively shared or otherwise exported orimported, allowing reuse in projects and other collaborative effortswith multiple composers, for example.

Various embodiments may be implemented, for example, using one or morewell-known computer systems, such as computer system 3900 shown in FIG.39. One or more computer systems 3900 may be used, for example, toimplement any of the embodiments discussed herein, as well ascombinations and sub-combinations thereof.

Computer system 3900 may include one or more processors (also calledcentral processing units, or CPUs), such as a processor 3904. Processor3904 may be connected to a bus or communication infrastructure 3906.

Computer system 3900 may also include user input/output device(s) 3903,such as monitors, keyboards, pointing devices, etc., which maycommunicate with communication infrastructure 3906 through userinput/output interface(s) 3902.

One or more of processors 3904 may be a graphics processing unit (GPU).In an embodiment, a GPU may be a processor that is a specializedelectronic circuit designed to process mathematically intensiveapplications. The GPU may have a parallel structure that is efficientfor parallel processing of large blocks of data, such as mathematicallyintensive data common to computer graphics applications, images, videos,vector processing, array processing, etc., including mathematical ormusical applications, for example.

Additionally, one or more of processors 3904 may include a coprocessoror other implementation of logic for accelerating calculations ofgenerating musical elements or other specialized mathematical functions,including hardware-accelerated coprocessors. Such accelerated processorsmay further include instruction set(s) for acceleration usingcoprocessors and/or other logic to facilitate such acceleration.

Computer system 3900 may also include a main or primary memory 3908,such as random access memory (RAM). Main memory 3908 may include one ormore levels of cache. Main memory 3908 may have stored therein controllogic (i.e., computer software) and/or data.

Computer system 3900 may also include one or more secondary storagedevices or secondary memory 3910. Secondary memory 3910 may include, forexample, a main storage drive 3912 and/or a removable storage device ordrive 3914. Main storage drive 3912 may be a hard disk drive orsolid-state drive, for example. Removable storage drive 3914 may be afloppy disk drive, a magnetic tape drive, a compact disk drive, anoptical storage device, tape backup device, and/or any other storagedevice/drive.

Removable storage drive 3914 may interact with a removable storage unit3918. Removable storage unit 3918 may include a computer usable orreadable storage device having stored thereon computer software (controllogic) and/or data. Removable storage unit 3918 may be a floppy disk,magnetic tape, compact disk, DVD, optical storage disk, and/any othercomputer data storage device. Removable storage drive 3914 may read fromand/or write to removable storage unit 3918.

Secondary memory 3910 may include other means, devices, components,instrumentalities or other approaches for allowing computer programsand/or other instructions and/or data to be accessed by computer system3900. Such means, devices, components, instrumentalities or otherapproaches may include, for example, a removable storage unit 3922 andan interface 3920. Examples of the removable storage unit 3922 and theinterface 3920 may include a program cartridge and cartridge interface(such as that found in video game devices), a removable memory chip(such as an EPROM or PROM) and associated socket, a memory stick and USBport, a memory card and associated memory card slot, and/or any otherremovable storage unit and associated interface.

Computer system 3900 may further include a communication or networkinterface 3924. Communication interface 3924 may enable computer system3900 to communicate and interact with any combination of externaldevices, external networks, external entities, etc. (individually andcollectively referenced by reference number 3928). For example,communication interface 3924 may allow computer system 3900 tocommunicate with external or remote devices 3928 over communication path3926, which may be wired and/or wireless (or a combination thereof), andwhich may include any combination of LANs, WANs, the Internet, etc.Control logic and/or data may be transmitted to and from computer system3900 via communication path 3926.

Computer system 3900 may also be any of a personal digital assistant(PDA), desktop workstation, laptop or notebook computer, netbook,tablet, smart phone, smart watch or other wearable, appliance, part ofthe Internet of Things (IoT), and/or embedded system, to name a fewnon-limiting examples, or any combination thereof.

Computer system 3900 may be a client or server, accessing or hosting anyapplications and/or data through any delivery paradigm, including butnot limited to remote or distributed cloud computing solutions; local oron-premises software (e.g., “on-premise” cloud-based solutions); “as aservice” models (e.g., content as a service (CaaS), digital content as aservice (DCaaS), software as a service (SaaS), managed software as aservice (MSaaS), platform as a service (PaaS), desktop as a service(DaaS), framework as a service (FaaS), backend as a service (BaaS),mobile backend as a service (MBaaS), infrastructure as a service (IaaS),database as a service (DBaaS), etc.); and/or a hybrid model includingany combination of the foregoing examples or other services or deliveryparadigms.

Any applicable data structures, file formats, and schemas may be derivedfrom standards including but not limited to JavaScript Object Notation(JSON), Extensible Markup Language (XML), Yet Another Markup Language(YAML), Extensible Hypertext Markup Language (XHTML), Wireless MarkupLanguage (WML), MessagePack, XML User Interface Language (XUL), or anyother functionally similar representations alone or in combination.Alternatively, proprietary data structures, formats or schemas may beused, either exclusively or in combination with known or open standards.

Any pertinent data, files, and/or databases may be stored, retrieved,accessed, and/or transmitted in human-readable formats such as numeric,textual, graphic, or multimedia formats, further including various typesof markup language, among other possible formats. Alternatively or incombination with the above formats, the data, files, and/or databasesmay be stored, retrieved, accessed, and/or transmitted in binary,encoded, compressed, and/or encrypted formats, or any othermachine-readable formats.

Interfacing or interconnection among various systems and layers mayemploy any number of mechanisms, such as any number of protocols,programmatic frameworks, floorplans, or application programminginterfaces (API), including but not limited to Document Object Model(DOM), Discovery Service (DS), NSUserDefaults, Web Services DescriptionLanguage (WSDL), Message Exchange Pattern (MEP), Web Distributed DataExchange (WDDX), Web Hypertext Application Technology Working Group(WHATWG) HTML5 Web Messaging, Representational State Transfer (REST orRESTful web services), Extensible User Interface Protocol (XUP), SimpleObject Access Protocol (SOAP), XML Schema Definition (XSD), XML RemoteProcedure Call (XML-RPC), or any other mechanisms, open or proprietary,that may achieve similar functionality and results.

Such interfacing or interconnection may also make use of uniformresource identifiers (URI), which may further include uniform resourcelocators (URL) or uniform resource names (URN). Other forms of uniformand/or unique identifiers, locators, or names may be used, eitherexclusively or in combination with forms such as those set forth above.

Any of the above protocols or APIs may interface with or be implementedin any programming language, procedural, functional, or object-oriented,and may be compiled or interpreted. Non-limiting examples include C,C++, C#, Objective-C, Java, Swift, Go, Ruby, Perl, Python, JavaScript,WebAssembly, or virtually any other language, with any other librariesor schemas, in any kind of framework, runtime environment, virtualmachine, interpreter, stack, engine, or similar mechanism, including butnot limited to Node.js, V8, Knockout, j Query, Dojo, Dijit, OpenUI5,AngularJS, Express.js, Backbonejs, Emberjs, DHTMLX, Vue, React,Electron, and so on, among many other non-limiting examples.

In some embodiments, a tangible, non-transitory apparatus or article ofmanufacture comprising a tangible, non-transitory computer useable orreadable medium having control logic (software) stored thereon may alsobe referred to herein as a computer program product or program storagedevice. This includes, but is not limited to, computer system 3900, mainmemory 3908, secondary memory 3910, and removable storage units 3918 and3922, as well as tangible articles of manufacture embodying anycombination of the foregoing. Such control logic, when executed by oneor more data processing devices (such as computer system 3900), maycause such data processing devices to operate as described herein.

Based on the teachings contained in this disclosure, it will be apparentto persons skilled in the relevant art(s) how to make and useembodiments of this disclosure using data processing devices, computersystems and/or computer architectures other than that shown in FIG. 39.In particular, embodiments may operate with software, hardware, and/oroperating system implementations other than those described herein.

It is to be appreciated that the Detailed Description section, and notany other section, is intended to be used to interpret the claims. Othersections may set forth one or more but not all exemplary embodiments ascontemplated by the inventor(s), and thus, are not intended to limitthis disclosure or the appended claims in any way.

While this disclosure describes exemplary embodiments for exemplaryfields and applications, it should be understood that the disclosure isnot limited thereto. Other embodiments and modifications thereto arepossible, and are within the scope and spirit of this disclosure. Forexample, and without limiting the generality of this paragraph,embodiments are not limited to the software, hardware, firmware, and/orentities illustrated in the figures and/or described herein. Further,embodiments (whether or not explicitly described herein) havesignificant utility to fields and applications beyond the examplesdescribed herein.

Embodiments have been described herein with the aid of functionalbuilding blocks illustrating the implementation of specified functionsand relationships thereof. The boundaries of these functional buildingblocks have been arbitrarily defined herein for the convenience of thedescription. Alternate boundaries may be defined as long as thespecified functions and relationships (or equivalents thereof) areappropriately performed. Also, alternative embodiments may performfunctional blocks, steps, operations, methods, etc. using orderingsdifferent from those described herein.

References herein to “one embodiment,” “an embodiment,” “an exampleembodiment,” “some embodiments,” or similar phrases, indicate that theembodiment described may include a particular feature, structure, orcharacteristic, but every embodiment may not necessarily include theparticular feature, structure, or characteristic. Moreover, such phrasesare not necessarily referring to the same embodiment.

Further, when a particular feature, structure, or characteristic isdescribed in connection with an embodiment, it would be within theknowledge of persons skilled in the relevant art(s) to incorporate suchfeature, structure, or characteristic into other embodiments whether ornot explicitly mentioned or described herein. Additionally, someembodiments may be described using the expression “coupled” and“connected” along with their derivatives. These terms are notnecessarily intended as synonyms for each other. For example, someembodiments may be described using the terms “connected” and/or“coupled” to indicate that two or more elements are in direct physicalor electrical contact with each other. The term “coupled,” however, mayalso mean that two or more elements are not in direct contact with eachother, but yet still co-operate or interact with each other.

The breadth and scope of the present disclosure should not be limited byany of the above-described exemplary embodiments, but should be definedonly in accordance with the following claims and their equivalents.

The invention claimed is:
 1. A computer-implemented method, comprising:retrieving, by at least one computer processor, via a memory, a firstconstraint value; receiving, by the at least one computer processor, viaa first module of a user interface, a selection of a set of musicalelements; accepting, by the at least one computer processor, via asecond module of the user interface, a second constraint valuecorresponding to the set of musical elements; storing, by the at leastone computer processor, the second constraint value in the memory;invoking, by the at least one computer processor, an iterator function,using at least the second constraint value as an argument; generating,by the at least one computer processor, an output of the iteratorfunction, wherein the output of the iterator function comprises at leastpart of a subset of the set of musical elements, wherein the subset isdetermined by the second constraint value; limiting, by the at least onecomputer processor, a size of the output of the iterator function,according to a lesser of the first constraint value or a transform ofthe second constraint value, wherein the size of the output of theiterator function is less than or equal to the first constraint value;storing, by the at least one computer processor, the output of theiterator function in the memory; and rendering, by the at least onecomputer processor, the output of the iterator function via a thirdmodule of the user interface.
 2. The computer-implemented method ofclaim 1, the rendering further comprising: emitting, by the at least onecomputer processor, via an audio adapter, a sequence of one or moresound signals based at least in part on the output of the iteratorfunction.
 3. The computer-implemented method of claim 1, the renderingfurther comprising: displaying, by the at least one computer processor,via a video adapter, a graphical representation of at least part of theoutput of the iterator function, a textual representation of at leastpart of the output of the iterator function, or a combination thereof.4. The computer-implemented method of claim 1, wherein the iteratorfunction is invoked in response to an input via the user interface, andwherein the output of the iterator function is not already stored in thememory.
 5. The computer-implemented method of claim 1, wherein themusical elements comprise a melody sequence, a chord, a chord note, achord sequence, a rhythm sequence, a syllable, or a combination thereof.6. The computer-implemented method of claim 1, further comprising:generating, by the at least one computer processor, metadata associatedwith at least one musical element of the output of the iteratorfunction; recording, by the at least one computer processor, in thememory, the metadata associated with the at least one musical element ofthe output of the iterator function.
 7. The computer-implemented methodof claim 6, wherein the metadata comprises an indication of whether agiven musical element of the output of the iterator function has beenrendered, a rating, an element descriptor, a component descriptor, or amood descriptor.
 8. The computer-implemented method of claim 1, whereinthe iterator function comprises a coroutine, a generator, or acombination thereof.
 9. The computer-implemented method of claim 1,wherein the transform comprises an enumerative combinatorial function.10. The computer-implemented method of claim 1, wherein the at least onecomputer processor is integrated in a digital audio workstation (DAW)apparatus.
 11. A non-transitory computer-readable storage mediumcomprising instructions stored thereon that, when executed by at leastone computer processor, cause the at least one computer processor toperform operations comprising: retrieving, via a memory, a firstconstraint value; receiving, via a first module of a user interface, aselection of a set of musical elements; accepting, via a second moduleof the user interface, a second constraint value corresponding to theset of musical elements; storing the second constraint value in thememory; invoking an iterator function, using at least the secondconstraint value as an argument; generating an output of the iteratorfunction, wherein the output of the iterator function comprises at leastpart of a subset of the set of musical elements, wherein the subset isdetermined by the second constraint value; limiting a size of the outputof the iterator function, according to a lesser of the first constraintvalue or a transform of the second constraint value, wherein the size ofthe output of the iterator function is less than or equal to the firstconstraint value; storing the output of the iterator function in thememory; and rendering the output of the iterator function via a thirdmodule of the user interface.
 12. The non-transitory computer-readablestorage medium of claim 11, the rendering further comprising: emitting,via an audio adapter, a sequence of one or more sound signals based atleast in part on the output of the iterator function.
 13. Thenon-transitory computer-readable storage medium of claim 11, therendering further comprising: displaying, via a video adapter, agraphical representation of at least part of the output of the iteratorfunction, a textual representation of at least part of the output of theiterator function, or a combination thereof.
 14. The non-transitorycomputer-readable storage medium of claim 11, wherein the iteratorfunction is invoked in response to an input via the user interface, andwherein the output of the iterator function is not already stored in thememory.
 15. The non-transitory computer-readable storage medium of claim11, wherein the musical elements comprise a melody sequence, a chord, achord note, a chord sequence, a rhythm sequence, a syllable, or acombination thereof.
 16. The non-transitory computer-readable storagemedium of claim 11, the operations further comprising: generatingmetadata associated with at least one musical element of the output ofthe iterator function; recording, in the memory, the metadata associatedwith the at least one musical element of the output of the iteratorfunction.
 17. The non-transitory computer-readable storage medium ofclaim 16, wherein the metadata comprises an indication of whether agiven musical element of the output of the iterator function has beenrendered, a rating, an element descriptor, a component descriptor, or amood descriptor.
 18. The non-transitory computer-readable storage mediumof claim 11, wherein the iterator function comprises a coroutine, agenerator, or a combination thereof.
 19. The non-transitorycomputer-readable storage medium of claim 11, wherein the transformcomprises an enumerative combinatorial function.
 20. The non-transitorycomputer-readable storage medium of claim 11, wherein the user interfaceis integrated in a digital audio workstation (DAW).
 21. A digital audioworkstation (DAW), comprising: a memory; and at least one computerprocessor configured to perform operations comprising: retrieving, viathe memory, a first constraint value; receiving, via a first module of auser interface, a selection of a set of musical elements; accepting, viaa second module of the user interface, a second constraint valuecorresponding to the set of musical elements; storing the secondconstraint value in the memory; invoking an iterator function, using atleast the second constraint value as an argument; generating an outputof the iterator function, wherein the output of the iterator functioncomprises at least part of a subset of the set of musical elements,wherein the subset is determined by the second constraint value;limiting a size of the output of the iterator function, according to[[the] ] a lesser of the first constraint value or a transform of thesecond constraint value, wherein the size of the output of the iteratorfunction is less than or equal to the first constraint value; storingthe output of the iterator function in the memory; and rendering theoutput of the iterator function via a third module of the userinterface.
 22. The DAW of claim 21, the rendering further comprising:emitting, via an audio adapter, a sequence of one or more sound signalsbased at least in part on the output of the iterator function.
 23. TheDAW of claim 21, the rendering further comprising: displaying, via avideo adapter, a graphical representation of at least part of the outputof the iterator function, a textual representation of at least part ofthe output of the iterator function, or a combination thereof.
 24. TheDAW of claim 21, wherein the iterator function is invoked in response toan input via the user interface, and wherein the output of the iteratorfunction is not already stored in the memory.
 25. The DAW of claim 21,wherein the musical elements comprise a melody sequence, a chord, achord note, a chord sequence, a rhythm sequence, a syllable, or acombination thereof.
 26. The DAW of claim 21, the operations furthercomprising: generating metadata associated with at least one musicalelement of the output of the iterator function; recording, in thememory, the metadata associated with the at least one musical element ofthe output of the iterator function.
 27. The DAW of claim 26, whereinthe metadata comprises an indication of whether a given musical elementof the output of the iterator function has been rendered, a rating, anelement descriptor, a component descriptor, or a mood descriptor. 28.The DAW of claim 21, wherein the iterator function comprises acoroutine, a generator, or a combination thereof.
 29. The DAW of claim21, wherein the transform comprises an enumerative combinatorialfunction.